All questions about the system may be directed to:
William W. Klaproth
1897 Joseph Drive
Moraga Ca. 94556
415/376-0708
B/O GPC
Oakland Ca.
Tie 8/648-5337
.eject
.space1
.TITLEA,3, BOWLING LEAGUE SECRETARY'S SYSTEM.page3,78,#1 SYSTEM OVERVIEW
This system is comprised of twelve programs, representingover 1600 lines of code. The system is written in ADVANCED BASICfor a 64K IBM Personal Computer with one or two disks and printer.
The system is highly generalized, permitting initializationof most items including:
League Name
Team Configuration
Handicap basis
Schedule
As distributed, the system can handle 18 teams, up to 5bowlers per team, and up to a 50 week season. The 18 team limitis a function of the 80 character print line width used to printschedules. If this function is appropriately modified, or notused, a much larger number of teams can be accommodated. Theactual limit is a function of diskette capacity, bowlers per team, and number of weeks.
Programs are provided to initialize all master files, enterscores and print standings (weekly), as well as prepare Bookaverage listings, final team/bowler standings, and display orprint individual team/bowler record sheets.
The system is designed to be used on either a one or two diskdrive system. Program selection is controlled by a master MENUprogram. The program diskette is assumed to be in the A drive. Except for the smallest leagues, you will need to maintain allbowler files on the B drive. In a single drive environment, DOSwill provide prompts to insert the appropriate diskette. Justremember - Drive A = PROGRAMS; Drive B = FILES.
.eject
.space1
SUMMARY OF FILE USAGE
*
* File 1 2 3 4 5 6
*
* TEAMS. BOWLERS. TEAM. BOWLER. HISCORES. SCHEDULE.
Program * HDR HDR DET .DET DET DET
---------- ----- ------ ---- ----- ------ ------
CREATE C C C C
SCHEDULE C
CHANGE U U
SCORES U U U U C
RECAP I I I I I I
RECORDD I I I I
RECORDP I I I I
SORTFILE I I I I
FINAL I I
PRINT I I
DETAIL I I I
The Table above contains a summary of file creation andusage. All bowling files are Random Files, and are written inpacked binary format. In the table above, "C" indicates where afile is created, "U" where it is updated, and "I" where it is used as input.
The following pages contain more detailed information on each file. The format column shows type of data representation:
I = Integer string
S = Single precision value string
D = Double precision value string
A = Character string
.eject
.space1
FILE DESCRIPTIONS
File # 1 - TEAMS.HDR (Team Header File)
From To Lgth Format Name Description
---- -- ---- ------ --------- -----------
RECORD NUMBER 1 - LEAGUE HEADER
1 2 2 I HDRID$ Header ID (Value="00")
3 32 30 A LEAGUE$ Name of League
33 34 2 I WEEKS$ Number of Weeks
35 36 2 I TEAMS$ Number of Teams
37 40 4 Not Used
41 42 2 I BWLPERTM$ Bowlers per Team
43 44 2 I NXTID$ Next Avail. ID
45 46 2 I HCPBASE$ Handicap Base
47 50 4 S HCPPCNT$ Handicap %
51 64 14 Not Used
RECORD 2 THRU nn - TEAM HEADERS
1 2 2 I TM$ Team Number
3 32 30 A NAM$ Team Name
33 34 2 I RCNT$ Number of Detail Records on File
35 36 2 I GAM$ Team Games Bowled
37 40 4 S PINS$ Total Team Pins
41 42 2 I AVG$ Team Average
43 44 2 I HIG$ High Team Game (Scratch)
45 46 2 I HIS$ High Team Series (Scratch)
47 50 4 S PTSW$ Total Team Points Won
51 54 4 S PTSL$ Total Team Points Lost
55 56 2 I B1ID$ ID Number of 1st Bowler
57 58 2 I B2ID$ ID Number of 2nd Bowler
59 60 2 I B3ID$ ID Number of 3rd Bowler
61 62 2 I B4ID$ ID Number of 4th Bowler
63 64 2 I B5ID$ ID Number of 5th Bowler
Record #1 on this file is the league header, which containsthe variable data for the entire league. The NXTID$ fieldindicates the next available bowler ID and is used by the CHANGEprogram when adding new bowler records. This field cannototherwise be updated.
Records 2 thru n contain Team header data. RCNT$ is acontrol filed and indicates the number of detail records on theTEAM.DET file. There is one header record per team. Its relative record address is the Team number + 1.
The ID numbers of bowlers assigned to each team are storedin the BxID$ fields which begin at position 55. Bowlers can beshifted among teams by changing these fields and the BTM$field in the BOWLERS.HDR record. (See description for file #2). NOTE: Total team pins (37-40) represents total pincount(including handicap). If scratch total pins is preferred, thelogic affecting this field may be found at lines 2050-2180 in theSCORES program.
.eject
.space1
FILE DESCRIPTIONS
File # 2 - BOWLERS.HDR (Bowler Header File)
From To Lgth Format Name Description
---- -- ---- ------ --------- -----------
1 2 2 I BBO$ Bowler Number
3 32 30 A BNAM$ Bowler Name
33 34 2 I BRCNT$ Number of Detail Records on File
35 36 2 I BGAM$ Total Games Bowled
37 40 4 S BPINS$ Total Pins
41 42 2 I BAVG$ Average
43 44 2 I BHIG$ High Game (Scratch)
45 46 2 I BHIS$ High Series (Scratch)
47 48 2 I BHCP$ Handicap
49 50 2 I BHIGH$ High Handicap Game
51 52 2 I BHISH$ High Handicap Series
53 54 2 I BTM$ Bowlers Team Number
55 56 2 I GAM2$ Number of 200 Games
57 58 2 I SER5$ Number of 500 Series
59 60 2 I SER6$ Number of 600 Series
61 62 2 I CURSER$ Current (Last) Series
63 64 2 I AVGLSTYR$ Average Last Year
This file contains one record per bowler and is updated bythe SCORES program. BHCP$ is initialized to 0 by CREATE andupdated with handicap only if 21 or more games have been bowled. The current series field (CURSER$) is also used to keep track ofconsecutive absences.
BTM$ indicates which team the bowler is assigned to. For asubstitute, this field is 0. Bowlers can easily be shifted amongteams and/or sub status by changing this field, as well as theBowler ID fields (pos 55-64) of the TEAMS.HDR records. Refer tothe section on File Relationships later in this chapter foradditional information.
BRCNT$ is a control field and indicates the number of detailrecords on the BOWLER.DET file..eject
.space1
FILE DESCRIPTIONS
File # 3 - TEAM.DET (Team Detail Records)
From To Lgth Format Name Description
---- -- ---- ------ --------- -----------
1 2 2 I DTM$ Team Number
3 4 2 I TMO$ Month
5 6 2 I TDAY$ Day
7 8 2 I TG1$ Team Game 1 Score
9 10 2 I TG2$ Team Game 2 Score
11 12 2 I TG3$ Team Game 3 Score
13 14 2 I TSER$ Team Series Score
15 16 2 I DPTSW$ Team Points Won
This file stores the weekly detail records for each team. A randomizing routine is used to compute record addresses. Up to50 weeks of detail records can be stored for each team. Game andseries scores stored in this file are handicap scores.
.eject
.space1
FILE DESCRIPTIONS
File # 4 - BOWLER.DET (Bowler Detail Records)
From To Lgth Format Name Description
---- -- ---- ------ --------- -----------
1 2 2 I DBO$ Bowler Number
3 4 2 I BMO$ Month
5 6 2 I BDAY$ Day
7 8 2 I BG1$ Game 1 Score
9 10 2 I BG2$ Game 2 Score
11 12 2 I BG3$ Game 3 Score
13 14 2 I BSER$ Series Score
15 16 2 I Not Used
This file contain weekly bowler detail records. Arandomizing routine is used to compute record address. Up to 50weeks of scores can be stored for each bowler. All scoresrecorded in this file are scratch scores.
.eject
.space1
FILE DESCRIPTIONS
File # 5 - HISCORES.DET (High Scores File)
From To Lgth Format Name Description
---- -- ---- ------ --------- -----------
1 2 2 I HBNO$ Bowler Number
3 4 2 I HG1$ Game 1 Score
5 6 2 I HG2$ Game 2 Score
7 8 2 I HG3$ Game 3 Score
9 10 2 I HSER$ Series Score
11 11 1 A HFLG1$ Game 1 Flag
12 12 1 A HFLG2$ Game 2 Flag
13 13 1 A HFLG3$ Game 3 Flag
14 14 1 A HFLGS$ Series Flag
15 16 2 I HCNT$ Flag Count
This file is created by SCORES and processed by RECAP. Onerecord is written for each bowler and contains the complete scoreand flags indicating the following mentionable high scores:
200+ game
500+ series
any game 50 pins or more above average
The logic associated with this file is located between lines1020-1390 in the SCORES program. The actual determination ofwhich scores to highlight is a function of the RECAP program.
.eject
.space1
File Descriptions
File # 6 - SCHEDULE.DET (Schedule File)
From To Lgth Format Name Description
---- -- ---- ------ --------- -----------
1 1 1 A STATUS$ Status (Reserved for future use
2 3 2 I WEEK$ Week number
4 5 2 I SMO$ Month
6 7 2 I SDY$ Day
8 75 68 A PRLINE$ Text line
This file is created at the begining of the season by theSCHEDULE program and is processed weekly by RECAP. A free formatis provided so that in addition to team pairings, special messages can be entered.
